ppppmmmmnnnneeeewwwwlllloooogggg may be used to stop and restart a running instance of
ppppmmmmllllooooggggggggeeeerrrr(1). This is most useful for managing multiple sets of
Performance Co-Pilot (PCP) arcive logs. These archive logs record the
history of performance metric values that may be ``played back'' by other
PCP tools, and they form the basis of the VCR paradigm and retrospective
performance analysis services common to the PCP toolkit.
In normal usage, ppppmmmmnnnneeeewwwwlllloooogggg would be executed by ccccrrrroooonnnn(1) in the wee hours
to terminate one PCP archive log and start another, i.e. to perform log
rotation.
Even more common, would be the execution of ppppmmmmnnnneeeewwwwlllloooogggg from the PCP archive
management script ccccrrrroooonnnn....ppppmmmmddddaaaaiiiillllyyyy(1). In this case, direct end-user
execution of ppppmmmmnnnneeeewwwwlllloooogggg is most unlikely.
The ppppmmmmllllooooggggggggeeeerrrr instance to be stopped and restarted must be running on the
same system as ppppmmmmnnnneeeewwwwlllloooogggg and is either the primary logger (the default) or
the logger with _p_i_d as specified by the ----pppp option.
The mandatory argument _a_r_c_h_i_v_e is the base name for the physical files
that will constitute the new archive log.
If no ----cccc option is specified, ppppmmmmnnnneeeewwwwlllloooogggg will use ppppmmmmllllcccc(1) to connect to the
running ppppmmmmllllooooggggggggeeeerrrr and so determine all those metrics and instances that
are subject to mmmmaaaannnnddddaaaattttoooorrrryyyy logging or aaaaddddvvvviiiissssoooorrrryyyy oooonnnn logging, and the
associated logging frequencies. This information is used to synthesize a
new ppppmmmmllllooooggggggggeeeerrrr configuration file. If the ----nnnn option is specified, it will
also be used for these interactions with ppppmmmmllllcccc.
If the ----cccc option is specified, ppppmmmmllllooooggggggggeeeerrrr will be restarted with _c_o_n_f_i_g_f_i_l_e
as the configuration file. Normally _c_o_n_f_i_g_f_i_l_e would be the same
configuration file used to start ppppmmmmllllooooggggggggeeeerrrr in the first place, however
note that since ppppmmmmllllooooggggggggeeeerrrr is restarted, any changes to the logging status
made using ppppmmmmllllcccc(1) will be lost, unless these have also been reflected in
changes to _c_o_n_f_i_g_f_i_l_e.
If _c_o_n_f_i_g_f_i_l_e does not exist, then a search is made in the directory
/_v_a_r/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r for a file of the same name, and if found that
file is used, e.g. if _c_o_n_f_i_g._m_u_m_b_l_e does not exist in the current
directory and the file /_v_a_r/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r/_c_o_n_f_i_g._m_u_m_b_l_e does exist,
then ----cccc ccccoooonnnnffffiiiigggg....mmmmuuuummmmbbbblllleeee and ----cccc ////vvvvaaaarrrr////ppppccccpppp////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....mmmmuuuummmmbbbblllleeee are